In the N4 Code Extensions view (on page 1), select all code extensions, and then Actions 
Compile Code Extensions
In the N4 Groovy Plug-ins view (on page 1), select all plug-ins, and then Actions Compile Groovy Plug-ins
To test Groovy code extensions after upgrading to a new release:
Do one or all of the following:
In the N4 Code Extensions view (on page 1), select all code extensions, and then Actions Compile Code Extensions
In the N4 Groovy Plug-ins view (on page 1), select all plug-ins, and then Actions Compile Groovy Plug-ins
This action prints a summary of the failures and successes. For example:
Summary of Groovy Compilation
SUCCESS : NavisUnitUpdateGroovyPlugin
SUCCESS : NavisGateGroovyPlugin
SUCCESS : NavisPrintReservedContainersGroovyPlugin
SUCCESS : NavisUnitRetireIDOEmail
SUCCESS : NavisUnitFixPodAndObCv
SUCCESS : NavisUnitDamageInsert
Stackkey=ERROR__NULL_MESSAGE parms=[Failed to parse groovy action:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed, script1300321791303.groovy: 6: unable to resolve class com.navis.xpscache.ParticipantCacheManager
Set up an IDE project (in Eclipse, IDEA, or any other IDE) that contains all of your Groovy scripts and the latest N4 .jar files. Then try to compile the project in the IDE. If it fails, this indicates incompatibility between N4 .jar files and the existing Groovy scripts.
Write an Ant project that performs the same function as the IDE above. For this, you need to download Ant from the Apache Web site and create an Ant project containing your Groovy scripts and the latest N4 .jar files. If the Ant project fails to compile the Groovy scripts, this indicates incompatibility. In this case, you should resolve any issues before you roll out the new N4 version into production.